Skip to content

Release {styler} 1.7.0 #930

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Mar 14, 2022
Merged

Release {styler} 1.7.0 #930

merged 6 commits into from
Mar 14, 2022

Conversation

lorenzwalthert
Copy link
Collaborator

@lorenzwalthert lorenzwalthert commented Mar 12, 2022

Prepare for release:

  • devtools::check_win_devel()
  • Polish NEWS
  • If new failures, update email.yml then revdepcheck::revdep_email_maintainers()
  • update cran-comments.md
  • run urlchecker::url_check("path/to/pkg")

Perform release:

  • Create RC branch (for bigger releases)
  • Bump version (in DESCRIPTION and NEWS)
  • add tidy thanks to NEWS.md
  • devtools::submit_cran()
  • pkgdown::build_site()
  • Approve email

Wait for CRAN...

  • Tag release
  • Merge RC back to master branch
  • Bump dev version
  • update CRAN speed change monitor PR.We have a new CRAN release coming up 🥳 See NEWS.md for new features.

@codecov-commenter
Copy link

codecov-commenter commented Mar 13, 2022

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.48%. Comparing base (afc969b) to head (795b4a4).
⚠️ Report is 792 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #930   +/-   ##
=======================================
  Coverage   90.48%   90.48%           
=======================================
  Files          47       47           
  Lines        2585     2585           
=======================================
  Hits         2339     2339           
  Misses        246      246           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions
Copy link
Contributor

This is how benchmark results would change (along with a 95% confidence interval in relative change) if be0a2be is merged into main:

  •   :ballot_box_with_check:cache_applying: 31.3ms -> 31.5ms [-2.43%, +3.33%]
  •   :ballot_box_with_check:cache_recording: 1.23s -> 1.24s [-0.46%, +1.04%]
  •   :ballot_box_with_check:without_cache: 3.33s -> 3.33s [-0.52%, +0.19%]

Further explanation regarding interpretation and methodology can be found in the documentation.

@github-actions
Copy link
Contributor

This is how benchmark results would change (along with a 95% confidence interval in relative change) if 01419a0 is merged into main:

  •   :ballot_box_with_check:cache_applying: 35.2ms -> 36ms [-2.38%, +6.99%]
  •   :ballot_box_with_check:cache_recording: 1.6s -> 1.61s [-0.31%, +1.33%]
  •   :ballot_box_with_check:without_cache: 4.39s -> 4.36s [-1.64%, +0.39%]

Further explanation regarding interpretation and methodology can be found in the documentation.

@github-actions
Copy link
Contributor

This is how benchmark results would change (along with a 95% confidence interval in relative change) if 6a474de is merged into main:

  •   :ballot_box_with_check:cache_applying: 22.1ms -> 22.1ms [-0.87%, +0.34%]
  •   :ballot_box_with_check:cache_recording: 960ms -> 959ms [-0.47%, +0.24%]
  •   :ballot_box_with_check:without_cache: 2.6s -> 2.6s [-0.55%, +0.6%]

Further explanation regarding interpretation and methodology can be found in the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants